Managing resources used during a development pipeline

ABSTRACT

Managing resources used during a development pipeline. A method of the disclosure includes analyzing historical resource usage of an application development system during different stages of a development pipeline for an application. The application development system includes a set of computing resources. The method also includes determining a current resource usage for a current stage of the development pipeline for the application. The method further includes determining an estimated resource usage for a later stage of the development pipeline for the application based on one or more of the current resource usage or the historical resource usage. The method further includes configuring the set of computing resources of the application development system for the later stage of the development pipeline based on the estimated resource usage.

TECHNICAL FIELD

Aspects of the present disclosure relate to development pipelines, andmore particularly, to managing resources used during different stages ofan application development pipeline.

BACKGROUND

An application may be one or more programs (e.g., computer programs),software, etc., that may be used by users, other applications, devices,etc., to perform various tasks, actions, functions, operations, methods,processes, calculations, etc. Examples of applications include webapplications, enterprise applications, consumer applications, mobileapplications, etc. An application may be divided into multiplecomponents, modules, portions, etc. Each component, module, portion,etc., may perform different functions, operations, actions, processes,methods, etc., for the application, and may provide different services,functionalities, or resources for the application.

BRIEF DESCRIPTION OF THE DRAWINGS

The described embodiments and the advantages thereof may best beunderstood by reference to the following description taken inconjunction with the accompanying drawings. These drawings in no waylimit any changes in form and detail that may be made to the describedembodiments by one skilled in the art without departing from the spiritand scope of the described embodiments.

FIG. 1 is a block diagram that illustrates an example developmentpipeline, in accordance with some embodiments of the present disclosure.

FIG. 2 is a block diagram that illustrates an example systemarchitecture, in accordance with some embodiments of the presentdisclosure.

FIG. 3 is a flow diagram of a method of managing resources of adevelopment system, in accordance with some embodiments of the presentdisclosure.

FIG. 4 is a flow diagram of a method of managing resources of adevelopment system, in accordance with some embodiments of the presentdisclosure.

FIG. 5 is a block diagram of an example computing device that mayperform one or more of the operations described herein, in accordancewith some embodiments of the present disclosure.

FIG. 6 is a block diagram of an example apparatus that may perform oneor more of the operations described herein, in accordance with someembodiments

DETAILED DESCRIPTION

As discussed above, an application may be one or more programs (e.g.,computer programs), software, etc., that may be used by users, otherapplications, devices, etc., to perform various tasks, actions,functions, operations, methods, processes, calculations, etc. Theapplication may be divided into components, modules, portions, etc.,that may perform different functions, operations, actions, processes,methods, etc., for the application, and may provide different services,functionalities, or resources for the application. The process or cyclefor developing (e.g., created, coded, implemented, etc.), testing, andmaintaining the application (or the modules and components of theapplication) may be referred to as a development pipeline. Thedevelopment pipeline may also be referred to as an applicationdevelopment pipeline, a development cycle, an application developmentcycle, etc.

A development system may be used to develop, test, deploy, or maintainan application. For example, a development system may be used byprogrammers or developers to implement (e.g., code) the application. Inanother example, the development system may be used by programmers ordevelopers to test portions or all of the application. In a furtherexample, the development system may be used to deploy the application tousers (e.g., to end users of the application). The development pipelinefor an application may include various stages or phases. Each stage orphase of the development pipeline may use computing resources of thedevelopment system. For example, each stage or phase of the developmentpipeline may use memory (e.g., random access memory (RAM)), storagespace, computing devices, network bandwidth, etc., of the developmentsystem.

If the computing resources used by each stage are allocated when thestage is reached, this may cause delays in the development pipeline. Forexample, a next stage in the development pipeline may not be able tostart until the computing resources (e.g., virtual machines, storagespace, memory, etc.) for the next stage are allocated. In addition, ifthe wrong amount of computing resources are allocated or reserved forthe next stage, this may waste computing resources and may also causedelays in the development pipeline. For example, if too many computingresources are allocated for a next or later stage, then the excesscomputing resources (e.g., excess virtual machines) may be wasted. Inanother example, if too few computing resources are allocated for thenext or later stage, then the next or later stage may take longer tocomplete due to the time taken to allocate additional computingresources for the next or later stage. Furthermore, many developmentsystems do not automatically allocate or reserve the resources used bylater stages of the development pipeline which may cause delays andinconvenience the users (e.g., programmers, developers, coders, testers,etc.) of the development system.

The present disclosure addresses the above-noted and other deficienciesby analyzing the computing resources used in previous iterations of thedevelopment pipelines for one or more applications. This may allow for abetter prediction or estimate of the computing resources that may beused in each stage of the development pipeline. This may also allow forbetter prediction of the correlation between the computing resourcesused in the different stages (e.g., the amount of computing resourcesused in one stage may be indicative of the amount of computing resourcesused in a second stage). The present disclosure also addresses theabove-noted and other deficiencies by determining an estimated resourceusage for the development system and configuring the resources of thedevelopment system (e.g., allocating or reserving resources) for next orlater stages, during a current stage of the development pipeline. Thismay reduce the amount of delays when the development system moves to thelater or next stage of the pipeline. This may further allow the users ofthe development system to have some advanced warning that there may beinsufficient resources for a next or later stage, which in turn allowsthe users to request or allocate additional resources for thedevelopment system.

FIG. 1 is a block diagram that illustrates an example developmentpipeline 100, in accordance with some embodiments of the presentdisclosure. As discussed above, an application may be one or moreprograms (e.g., computer programs), software, software applications,etc., that may be used by users, other applications, devices, etc., toperform various tasks, actions, functions, operations, methods,processes, calculations, etc. The process or cycle for developing (e.g.,created, coded, implemented, etc.), testing, deploying, and maintainingan application may be referred to as a development pipeline. Thedevelopment pipeline (or process) may be a cyclical pipeline, asdiscussed in more detail below. One type of development pipe line may bea continuous integration continuation delivery (CI/CD) pipeline. A CI/CDpipeline may be a pipeline or process where an application, or modulesand components of the application, are built (e.g., compiled), tested,and deployed (e.g., released to users) in shorter time periods. Forexample, new code for the application may be built, tested, and deployedevery few hours, every day, or every appropriate time period. Thetesting of the application, or modules and components of theapplication, may be performed when code (e.g., source code, programingcode, etc.) is checked into a version control system (e.g., a sourcecontrol system, a code repository, etc.). For example, testing of theapplication may be performed automatically when new code for theapplication is checked in. The deployment of the application, or modulesand components of the application may be performed when the testing ofthe application (or modules and components of the application) has beencompleted. For example, the application may be automatically deployedwhen the testing of the application has been completed.

In one embodiment, the development pipeline 100 illustrated in FIG. 1may be an example of a CI/CD pipeline. The development pipeline 100includes a development stage 105, a unit testing stage 110, anintegration testing stage 115, a system testing stage 120, and adeployment stage 125. The stages illustrated in FIG. 1 are merelyexamples, and different stages may be used in the development pipeline100 in other embodiments. For example, additional stages may be includedin the development pipeline 100. In another example, one of the stagesin the development pipeline 100 may be divided into multiple stages.

In one embodiment, developers, coders, programmers, etc., may modify theapplication during the development stage 105. For example, developersmay write code, add code, update code, modify code, fix bugs, add newfeatures, add security fixes, enhance existing features, etc., duringthe development stage 105. The development stage 105 may end when thedevelopers, coders, programmers, etc., check in code to a versioncontrol system (e.g., a source control system, a code repository, etc.).In one embodiment, one or more components, modules, units, portions,etc., of the application may be testing during the unit testing stage110. For example, smaller portions (e.g., single modules) of theapplication may be tested during the unit testing stage 110. The unittesting stage 110 may start after the development stage 105. Forexample, unit tests (for the unit testing stage 110) may beautomatically started or performed after the developers, coders,programmers, etc., check in their code to the version control system.

In one embodiment, individual components, modules, units, portions,etc., of the application may be combined and tested as a group duringthe integration testing stage 115. For example, multiple modules (e.g.,two, three, or some other appropriate number of modules) may be combinedand tested together as a single module. The integration testing stage115 may start after the unit tests for the individual components,modules, units, portions, etc., of the application that are to becombined and tested as a group are completed. For example, integrationtesting stage 115 may start after all or a threshold number of the unittests for the individual components, modules, units, portions, etc., ofthe application, have passed.

In one embodiment, the complete or integrated application may be testedduring the system testing stage 120. During the system testing stage120, the application may be tested to determine if the application is incompliance with different requirements. For example, the application maybe tested to determine whether certain features operate as specified ina design document. In another example, the application may be tested todetermine whether the application can perform different operations,functions, actions, etc., within a specified period of time.

In one embodiment, the application may be deployed (e.g., installed,updated, etc.) onto various computing devices during the deploymentstage 125. For example, the application or portions of the applicationmay be installed on to different server computing devices, clientcomputing devices, etc., during the deployment stage 125. The deploymentstage 125 may include various types of deployments. For example, thedeployment stage 125 may include a test deployment where the applicationis deployed to a subset of computing devices that have the applicationinstalled. This may allow the developers to see how the applicationperforms on the subset of computing devices before deploying theapplication to all of the computing devices that have the applicationinstalled.

In one embodiment, the development pipeline 100 may be a cyclicalpipeline or processes. For example, the development pipeline 100 mayproceed from the deployment stage 125 back to the development stage 105,after the deployment stage 125 has been completed. Thus, a later stagein the development pipeline 100 may refer to an earlier stage in thedevelopment pipeline. For example, a later stage after the deploymentstage 125 may refer to the development stage 105 of the unit testingstage 110.

As discussed above, the development pipeline 100 may include fewer,more, or different stages than those illustrated in FIG. 1. For example,the development pipeline 100 may include a stress testing stage (e.g.,tests are performed repeatedly on the application or modules of theapplication), a soak testing stage (where the tests are performed over alonger period of time to determine whether an application or modules ofthe application are stable), etc. In another example, the deploymentstage 125 may be divided into multiple stages (e.g., the deploymentstage 125 may be divided into a small scale deployment stage to test outthe deployment of the application by deploying the application to asubset of users, and a full scale deployment stage where the applicationmay be deployed to all users of the application).

FIG. 2 is a block diagram that illustrates an example systemarchitecture 200, in accordance with some embodiments of the presentdisclosure. The system architecture 200 includes a development system201 and computing device 280. The development system 201 includescomputing devices 220 and 230, a data store 260 and a network 205. Thecomputing devices 220 and 230, and the data store 260 may be coupled toeach other (e.g., may be operatively coupled, communicatively coupled,may communicate data/messages with each other) via network 205. Network205 may be a public network (e.g., the internet), a private network(e.g., a local area network (LAN) or wide area network (WAN)), or acombination thereof. In one embodiment, network 205 may include a wiredor a wireless infrastructure, which may be provided by one or morewireless communications systems, such as a wireless fidelity (Wi-Fi)hotspot connected with the network 205 and/or a wireless carrier systemthat can be implemented using various data processing equipment,communication towers (e.g. cell towers), etc. The network 205 may carrycommunications (e.g., data, message, packets, frames, etc.) betweencomputing devices 220 and 230, and the data store 260. The data store260 may be a persistent storage that is capable of storing data. Apersistent storage may be a local storage unit or a remote storage unit.Persistent storage may be a magnetic storage unit, optical storage unit,solid state storage unit, electronic storage units (main memory), orsimilar storage unit. Persistent storage may also be a monolithic/singledevice or a distributed set of devices. The computing device 280 may becoupled to the development system 201 via another network or via thenetwork 205. Although the computing device 280 (and the resourcecomponent 281) is illustrate as separate from the development system210, the computing device 280 (and the resource component 281) may bepart of the development system 210 in other embodiments.

Each computing device (e.g., computing devices 220, 230, and 280) mayinclude hardware such as processing devices (e.g., processors, centralprocessing units (CPUs), memory (e.g., random access memory (RAM),storage devices (e.g., hard-disk drive (HDD), solid-state drive (SSD),etc.), and other hardware devices (e.g., sound card, video card, etc.).The computing devices may comprise any suitable type of computing deviceor machine that has a programmable processor including, for example,server computers, desktop computers, laptop computers, tablet computers,smartphones, set-top boxes, etc. In some examples, the computing devicesmay comprise a single machine or may include multiple interconnectedmachines (e.g., multiple servers configured in a cluster). Eachcomputing device may execute or include an operating system (OS), asdiscussed in more detail below. The OS of a computing device may managethe execution of other components (e.g., software, applications, etc.)and/or may manage access to the hardware (e.g., processors, memory,storage devices etc.) of the computing device.

As illustrated in FIG. 2, computing devices 220 include virtualenvironments 223. In one embodiment, a virtual environment 223 may be avirtual machine (VM) that may execute on a hypervisor which executes ontop of the OS for a computing device. The hypervisor may also bereferred to as a virtual machine monitor (VMM). A VM may be a softwareimplementation of a machine (e.g., a software implementation of acomputing device) that includes its own operating system (referred to asa guest OS) and executes application programs, applications, software. AVM may be, for example, a hardware emulation, a full virtualization, apara-virtualization, and an operating system-level virtualization VM.The hypervisor may be a component of an OS for a computing device, mayrun on top of the OS for a computing device, or may run directly on hosthardware without the use of an OS. The hypervisor may manage systemresources, including access to hardware devices such as physicalprocessing devices (e.g., processors, CPUs, etc.), physical memory(e.g., RAM), storage device (e.g., HDDs, SSDs), and/or other devices(e.g., sound cards, video cards, etc.). The hypervisor may also emulatethe hardware (or other physical resources) which may be used by the VMsto execute software/applications. For example, the hypervisor, thoughtypically implemented in software, may emulate and export a bare machineinterface to higher level software in the form of virtual processors andguest memory. Higher level software may comprise a standard or real-timeoperating system (OS), may be a highly stripped down operatingenvironment with limited operating system functionality, may not includetraditional OS facilities, etc. Hypervisor 212 may present othersoftware (i.e., “guest” software) the abstraction of one or more virtualmachines (VMs) that provide the same or different abstractions tovarious guest software (e.g., guest operating system, guestapplications). VM 213 may execute guest software that uses an underlyingemulation of the physical resources (e.g., virtual processors and guestmemory).

In another embodiment, a virtual environment 223 may be a container thatmay execute on a container engine which executes on top of the OS for acomputing device, as discussed in more detail below. A container may bean isolated set of resources allocated to executing an application,software, and/or process independent from other applications, software,and/or processes. The host OS (e.g., an OS of the computing device) mayuse namespaces to isolate the resources of the containers from eachother. A container 223 may also be a virtualized object similar tovirtual machines. However, a container may not implement separate guestOS (like a VM). The container may share the kernel, libraries, andbinaries of the host OS with other containers that are executing on thecomputing device. The container engine may allow different containers toshare the host OS (e.g., the OS kernel, binaries, libraries, etc.) of acomputing device. For example, the container engine may multiplex thebinaries and/or libraries of the host OS between multiple containers.The container engine may also facilitate interactions between thecontainer and the resources of the computing device. For example, thecontainer engine may manage requests from container to access a memory(e.g., a RAM) of the computing device 110. In another example, thecontainer engine may manage requests from the container to accesscertain libraries/binaries of the host OS. The container engine may alsobe used to create, remove, and manage containers. In one embodiment, thecontainer engine may be a component of a host operating system. Inanother embodiment, container engine may run on top of a host operatingsystem, or may run directly on host hardware without the use of a hostoperating system.

As discussed above, the development system 210 may be used to develop,update, test, deploy, and maintain one or more applications (e.g.,software, software applications, apps, web applications, mobileapplications, mobile apps, etc.). Also as discussed above, the processof developing, testing, deploying, etc., applications may be referred toas a development pipeline. The development pipeline may have variousstages (e.g., phases) and each stage may use resources (e.g., computingresources, such as RAM, storage space, processing power, networkbandwidth, computing devices, VMs, containers, etc.) of the developmentsystem 210.

In one embodiment, the resource component 281 may analyze the historicalresource usage of the development system 210. For example, the resourcecomponent 281 may analyze the computing resources previously used by thedevelopment system 210 during different stages of the developmentpipelines for one or more applications. As discussed above, thedevelopment system 210 includes computing resource (e.g., a set ofcomputing resources), such as computing devices, processing power (e.g.,processing devices, CPUs, virtual processing devices, etc.), VMs,containers, memory (e.g., RAM), storage space (e.g., disk space, harddrive space, flash drive space, etc.), network bandwidth, etc. Theresource component 281 may analyze the number of computing devices, theamount of memory (e.g., the amount of RAM), the amount of storage space(e.g., the amount of hard drive space), the amount of data transmittedand received via the network 205, etc., during the development stage,unit testing stage, integration testing stage, system testing stage, anddeployment stage of the development pipeline.

In some embodiments, the resource component 281 may determinecorrelations, relationships, dependencies, etc., between the amounts ofcomputing resources used in different stages of the developmentpipeline, based on the analysis of the historical resource usage. Forexample, the resource component 281 may determine that there isgenerally a linear increase in computing resource usage as thedevelopment stage progresses through the development pipeline. Inanother example, the resource component 218 may determine that one stageof the development pipeline uses a certain percentage (e.g., 75%, 125%,or some other appropriate percentage) of the computing resources used byanother stage of the development pipeline. The resource component 281may use various techniques, methods, algorithms, etc., to determinecorrelations, relationships, dependencies, etc., between the amounts ofcomputing resources used in different stages of the development pipelinefor various applications. For example, the resource component 281 mayuse machine learning, artificial intelligence, statistical models,neural networks, clustering techniques, etc.

In one embodiment, the resource component 281 may determine the currentresource usage for a current stage of the development pipeline for anapplication. For example, an application may currently be at aparticular stage of the development pipeline for the application (e.g.,a development stage, an integration testing stage, etc.). The resourcecomponent 281 may determine the number of computing devices 220 or 230used, the number of virtual environment 223 used, the amount of memoryin the computing devices 220 or 230, the number of processing devices,etc., used for the particular stage of the development pipeline (e.g.,for the current stage).

In one embodiment, the resource component 281 may determine an estimatedresource usage for a later stage of the development pipeline for theapplication. For example, the resource component 281 may analyzeprevious iterations of the development pipeline to determine the amountor number of resources used for the same stage of the developmentpipeline (e.g., for the later or particulate stage in previousiterations of the development pipeline). In another example, theresource component 281 may determine whether the current stage of thedevelopment pipeline may provide one or more indications of the amountor number of resources that may be used in the later stage of thedevelopment pipeline. In a further example, the resource component 281may analyze computing resources used in development pipelines for otherapplications (e.g., other applications that may perform similarfunctions, may use similar libraries or software modules, etc.).

In some embodiments, the later stage of the development pipeline may bea next stage (e.g., the very next stage) in the development pipeline ofthe application. In other embodiments, the later stage of thedevelopment pipeline may be not be a next stage but may be after thecurrent stage in the development pipeline of the application. For, theresource component 281 may determine an estimated resource usage for oneor more a unit testing stage, an integration testing stage, a systemtesting stage, or a deployment stage (e.g., for a later stage) during adevelopment stage (e.g., a current stage). In another example, theresource component 281 may determine an estimated resource usage for oneor more an integration testing stage, a system testing stage, or adeployment stage (e.g., for a later stage) during a unit testing stage(e.g., a current stage). In a further example, the resource component281 may determine an estimated resource usage for one or more a systemtesting stage and a deployment stage (e.g., for a later stage) during anintegration testing stage (e.g., a current stage). In yet anotherexample, resource component 281 may determine an estimated resourceusage for a deployment stage (e.g., for a later stage) during a systemtesting stage (e.g., a current stage).

In one embodiment, the resource component 281 may determine theestimated resource usage for a later stage (e.g., the next stage, astage that is two stages later than the current stage, etc.) while thedevelopment system 210 is performing functions, operations, actions,tasks, methods, etc., for a current stage. For example, while thedevelopment system 210 is performing one or more units tests during aunit testing stage (e.g., a current stage), the resource component 281may simultaneously determine the estimated resource usage for anintegration testing stage (e.g., a later stage or a next stage). Inanother example, while the development system 210 is performing one ormore units tests during an integration testing stage (e.g., a currentstage), the resource component 281 may simultaneously determine theestimated resource usage for deployment stage (e.g., a later stage). Insome embodiments, the resource component 281 may automatically determinethe estimated resource usage for the later stage (or the next stage) ata certain point or time period within the current stage. For example,resource component 281 may automatically determine the estimatedresource usage for the later stage when the development system 210 is75% of the way through the current stage, or within 10 minutes offinishing the current stage.

In one embodiment, the resource component 281 may determine whether thecomputing resources of the development system 210 are sufficient for thelater stage of the development pipeline. The resource component 281 maydetermine whether the computing resources of the development system 210are sufficient for the later stage based on the estimated resource usagedetermined (e.g., calculated) for the later stage. For example, theresource component 281 may determine an estimated amount of resources(e.g., an estimated amount of RAM, storage space, processing devices,client devices, VMs, etc.) that may be used during the later stage ofthe development pipeline. The resource component 281 may determinewhether the development system 210 has enough resources (e.g., hassufficient resources) for the next stage. For example, the resourcecomponent 281 may determine whether there are enough free or availableresources for the next stage. In another example, the resource component281 may determine whether the total resources of the development system(e.g., both currently used and free resources) are sufficient for thenext or later stage.

In one embodiment, the resource component 281 may provide an indicationto one or more users of the system architecture 200, in response todetermining that the computing resources of development system are notsufficient for later stage of the development pipeline based on theestimated resource usage. For example, the resource component 281 mayestimate that two gigabytes of storage space may be used by theintegration testing stage (e.g., a next stage or a later stage in theapplication development pipeline) because one gigabyte of storage spaceused during the unit testing stage (e.g., a current stage). The resourcecomponent 281 may determine whether the one or more of the computingdevices 220 and 230 has two gigabytes of storage space. For example, theresource component 281 may determine whether a computing device 220 hastwo gigabytes of free storage space. In another example, the resourcecomponent 281 may determine whether the computing device 220 can free upor reallocate two gigabytes of storage space, etc.). If the resourcecomponent 281 determines that the computing device 220 and 230 does nothave two gigabytes of storage space for the integration testing stage,the resource component 281 may provide an indication to a user of thesystem architecture 200, indicating that the estimated amount of spaceis not available. For example, the resource component may present adisplay a message (e.g., an error message, a warning message, etc.) viaa graphical user interface (GUI) of the resource component 281. Inanother example, the resource component 281 may transmit a message(e.g., an email, a chat message, a text message, etc.) to one or moreusers of the development system 210 indicating that the developmentsystem 210 does not have sufficient resources for the next or laterstage.

In one embodiment, the resource component 281 may configure the set ofcomputing resources of the development system 210 based on the estimatedresource usage. For example, if the resource component 281 determinesthat an estimated amount of resources will be used by the developmentsystem (e.g., determines the estimated resource usage) in the later ornext stage, the resource component 281 may configure the estimatedamount of resources in preparation for the later or next stage. Theresource component 281 may configure the set of computing resources inresponse to determining that the development system 210 has sufficientresources for the next stage or later stage. For example, the resourcecomponent 281 may configure the set of computing resources in responseto determining that the development system 210 has enough availableresources (e.g., enough free resources) or can allocate enough resourcesto satisfy or meet the estimated resource usage, as discussed in moredetail below. The resource component 281 may configure the set ofcomputing resources of the development system 210 for the next or laterstage, during the current stage. For example, the resource component 281may configure the set of computing resources of the development system210 for the next or later stage, while the current stage is in progress(e.g., simultaneous with the current stage).

In some embodiments, the resource component 281 may configure theestimated amount of resources by allocating the estimated amount ofresources. Allocating the estimated amount of resources may includeallocating storage space, allocating memory space (e.g., allocating anamount of RAM), allocating processing devices (e.g., allocating CPUs orvirtual CPUs), allocating VMs (e.g., creating one or more VMs),allocating containers (e.g., creating one or more containers), etc.

In other embodiments, the resource component 281 may configure theestimated amount of resources by reserving the estimated amount ofresources of the development system 210. Reserving the estimated amountof resources may include setting a flag, parameter, indicator, etc.,that one or more resources are to be used for the later or next stage ofthe development pipeline. This may help prevent the resources from beingallocated for other purposes. For example, this may prevent theresources from being allocated to another development stage of anotherapplication. Other appropriate methods, actions, functions, operations,etc., for reserving a resource (e.g., updating a schedule or table,etc.) may be used to reserve or hold one or more resources for the lateror next stage of the development pipeline in other embodiments.

In further embodiments, resource component 281 may configure theestimated amount of resources by reallocating resources that were usedin previous stages of the development pipeline for the application. Forexample, the development system 210 may currently be in a unit testingstage for an application. The development system 210 may use a number ofVMs (e.g., resources) during the unit testing stage. One or more of theVMs used during the unit testing stage may be reused or reallocated foran integration testing phase (e.g., for a next phase). The resourcesthat were used for other development pipelines of other applications(which may also be using the development system 210) may also be reusedor reallocated for the next or later stage of the application.

As discussed above, the resource component 281 may automaticallydetermine the estimated resource usage of a next or later stage. Forexample, the resource component 281 may automatically determine theestimated resource usage of a next stage of the development pipelinewhen the development system 210 reaches a threshold point within thecurrent stage (e.g., when the development system 210 is halfway througha current stage) or has performed a threshold number of actions,functions, operations, etc., for the current stage (e.g., when thedevelopment system has performed 80% of the tests in a unit testingstage). In another example, the resource component 281 may automaticallydetermine the estimated resource usage of the next stage when thedevelopment system 210 is within a threshold time of completing thecurrent stage (e.g., when the development system 210 is within twohours, twenty minutes, or some other appropriate time of completing thecurrent stage). Also as discussed above, the resource component 210 mayautomatically configure one or more of the resources of the developmentsystem 210 for the next or later stage. For example, the resourcecomponent 281 may automatically configure one or more of the resourcesof the development system 210 for the next or later stage when thedevelopment system 210 reaches a threshold point within the currentstage (e.g., when the development system 210 is three quarters of theway through a current stage) or has performed a threshold number ofactions, functions, operations, etc., for the current stage (e.g., whenthe development system has performed 90% of the tests in a unit testingstage). In another example, the resource component 281 may automaticallyconfigure one or more of the resources of the development system 210 forthe next or later stage when the development system 210 is within athreshold time of completing the current stage (e.g., when thedevelopment system 210 is within five minutes or some other appropriatetime of completing the current stage). The resource component 281 maydetermine the estimated resource usage of a next or later stage and mayconfigure one or more resources of the development system 210 atdifferent times in the current stage.

The examples, embodiments, implementations, etc., described herein mayallow users of the development system 210 (e.g., programmers,developers, etc., who are implementing, coding, writing, and testing anapplication) to more efficiently use the development system 210. Bydetermining (e.g., automatically determining) an estimated resourceusage of a next or later stage of a development pipeline and configuring(e.g., automatically configuring) the resources for the next or latestage, this may allow the development system 210 to help ensure theresources are allocated for the next stage so that there are fewerdelays in the stages of the development pipeline. This may allow for abetter prediction or estimate of the computing resources that may beused in each stage of the development pipeline. This may further allowfor better prediction of the correlation between the computing resourcesused in the different stages (e.g., the amount of computing resourcesused in one stage may be indicative of the amount of computing resourcesused in a second stage). This may further allow the users of thedevelopment system 210 to have some advanced warning that there may beinsufficient resources for a next or later stage, which in turn allowsthe users to request or allocate additional resources for thedevelopment system 210.

FIG. 3 is a flow diagram of a method 300 of operating a web applicationin accordance with some embodiments. Method 300 may be performed byprocessing logic that may comprise hardware (e.g., circuitry, dedicatedlogic, programmable logic, a processor, a processing device, a centralprocessing unit (CPU), a system-on-chip (SoC), etc.), software (e.g.,instructions running/executing on a processing device), firmware (e.g.,microcode), or a combination thereof. In some embodiments, the method300 may be performed by a resource component (e.g., resource component281 illustrated in FIG. 2) and/or a computing device (e.g., computingdevice 280 illustrated in FIG. 2).

The method 300 begins at block 305, where the method 300 analyzes thehistorical resource usage of the application development system, asdiscussed above. For example, the method 300 may analyze that amount ofresources used by the application development system for previousiterations of an application development pipeline for an application. Inanother example, the method 300 may analyze the amount of resources usedby the application development system for previous iterations ofapplication development pipelines for other applications that may besimilar to the current application (e.g., other applications that mayuse the same libraries, same modules, perform the same functions oroperations, etc.). At block 310, the method 300 may determine thecurrent resource usage for a current stage of the development pipeline,as discussed above. For example, the method 300 may determine the amountof memory (e.g., RAM), storage space, processing power, VMs, containers,etc., used during the current stage of the development pipeline for theapplication.

At block 315, the method 300 may determine an estimated resource usagefor a later stage of the development pipeline, based on one or more ofthe historical resource usage and the current resource usage of thedevelopment system, as discussed above. For example, the historicalresource usage for the development system may indicate that the nextstage in the development pipeline will typically use two times theprocessing power as the current stage in the development pipeline. Themethod 300 determine (e.g., may estimate) that the processing power usedfor the next stage will be two times of current processing power usedfor the current stage. At block 320, the method 300 may configure thecomputing resources of the development system (e.g., the set ofcomputing resources that the development system may use) based on theestimated resource usage, as discussed above. For example, if estimatedresource usage was 50 gigabytes (GB) of storage space for the next (orlater) stage of the development pipeline, the method 300 may allocate 50GB of storage space in preparation of the next stage of the developmentpipeline. In another example, the method 300 may reserve or otherwiseindicate that resources of the development system will be allocated forthe next (or later) stage. For example, if a VM is being used for thecurrent stage, the method 300 may set a flag or parameter, update atable, etc., to indicate that the VM should be reserved for the next (orlater) stage.

FIG. 4 is a flow diagram of a method 400 of operating a web applicationin accordance with some embodiments. Method 400 may be performed byprocessing logic that may comprise hardware (e.g., circuitry, dedicatedlogic, programmable logic, a processor, a processing device, a centralprocessing unit (CPU), a system-on-chip (SoC), etc.), software (e.g.,instructions running/executing on a processing device), firmware (e.g.,microcode), or a combination thereof. In some embodiments, the method400 may be performed by a resource component (e.g., resource component281 illustrated in FIG. 2) and/or a computing device (e.g., computingdevice 280 illustrated in FIG. 2).

The method 400 begins at block 405, where the method 400 may determinean estimated resource usage for a later stage of a development pipeline,based on one or more of the historical resource usage and the currentresource usage of a development system, as discussed above. For example,the historical resource usage for the development system may indicatethat the next or later stage in the development pipeline will typicallyuse three times the storage space as the current stage in thedevelopment pipeline. The method 400 determine (e.g., may estimate) thatthe storage used for the next or later stage will be three times ofcurrent storage space used for the current stage.

At block 410, the method 400 may determine whether the computingresources (e.g., the set of computing resources) of the developmentsystem are sufficient for the later (or next) stage of the developmentpipeline based on the estimated resource usage. For example, the method400 may determine whether there are enough free (e.g., unused) resourcesavailable, based on the estimated resource usage. In another example,the method 400 may determine whether the total amount of resources inthe development system would be sufficient, based on the estimatedresource usage (e.g., whether there are enough available, and enoughcurrently used resources that can be reserved or reallocated). If thecomputing resources of the development system are sufficient for thenext or later stage, the method 400 may configure the computingresources of the development system (e.g., the set of computingresources that the development system may use) based on the estimatedresource usage at block 415, as discussed above. For example, the method400 may allocate or reserve resources for the next stage of thedevelopment pipeline. If the computing resources of the developmentsystem are not sufficient for the next or later stage, the method 400may provide an indication that the computing resources are insufficientfor the next or later stage, to one or more users of the developmentsystem at block 420. For example, the method 400 may present or displaya message (e.g., an error message, a warning message, an informationalmessage, etc.) to one or more users of the development system via a GUI.This may allow the users of the development system to have advancedwarning or notice that the development system may not have enoughcomputing resources for the next or later stage. For example, this mayallow the users to have an indication that the computing resources maybe insufficient for a later stage, before the later stage is reached.This may also allow the users of the development system to requestadditional computing resources in preparation for the later or nextstage. For example, this may allow users to request additional computingresources from a datacenter or a cloud computing architecture, beforethe later or next stage is reached.

FIG. 5 is a block diagram of an example computing device 500 that mayperform one or more of the operations described herein, in accordancewith some embodiments. Computing device 500 may be connected to othercomputing devices in a LAN, an intranet, an extranet, and/or theInternet. The computing device may operate in the capacity of a servermachine in client-server network environment or in the capacity of aclient in a peer-to-peer network environment. The computing device maybe provided by a personal computer (PC), a set-top box (STB), a server,a network router, switch or bridge, or any machine capable of executinga set of instructions (sequential or otherwise) that specify actions tobe taken by that machine. Further, while only a single computing deviceis illustrated, the term “computing device” shall also be taken toinclude any collection of computing devices that individually or jointlyexecute a set (or multiple sets) of instructions to perform the methodsdiscussed herein.

The example computing device 500 may include a processing device (e.g.,a general purpose processor, a PLD, etc.) 502, a main memory 504 (e.g.,synchronous dynamic random access memory (DRAM), read-only memory(ROM)), a static memory 506 (e.g., flash memory and a data storagedevice 518), which may communicate with each other via a bus 530.

Processing device 502 may be provided by one or more general-purposeprocessing devices such as a microprocessor, central processing unit, orthe like. In an illustrative example, processing device 502 may comprisea complex instruction set computing (CISC) microprocessor, reducedinstruction set computing (RISC) microprocessor, very long instructionword (VLIW) microprocessor, or a processor implementing otherinstruction sets or processors implementing a combination of instructionsets. Processing device 502 may also comprise one or morespecial-purpose processing devices such as an application specificintegrated circuit (ASIC), a field programmable gate array (FPGA), adigital signal processor (DSP), network processor, or the like. Theprocessing device 502 may be configured to execute the operationsdescribed herein, in accordance with one or more aspects of the presentdisclosure, for performing the operations and steps discussed herein.

Computing device 500 may further include a network interface device 508which may communicate with a network 520. The computing device 500 alsomay include a video display unit 510 (e.g., a liquid crystal display(LCD) or a cathode ray tube (CRT)), an alphanumeric input device 512(e.g., a keyboard), a cursor control device 514 (e.g., a mouse) and anacoustic signal generation device 516 (e.g., a speaker). In oneembodiment, video display unit 510, alphanumeric input device 512, andcursor control device 514 may be combined into a single component ordevice (e.g., an LCD touch screen).

Data storage device 518 may include a computer-readable storage medium528 on which may be stored one or more sets of instructions, e.g.,instructions for carrying out the operations described herein, inaccordance with one or more aspects of the present disclosure.Instructions 526 implementing a resource component (e.g., resourcecomponent 281 illustrated in FIG. 2) may also reside, completely or atleast partially, within main memory 504 and/or within processing device502 during execution thereof by computing device 500, main memory 504and processing device 502 also constituting computer-readable media. Theinstructions may further be transmitted or received over a network 520via network interface device 508.

While computer-readable storage medium 528 is shown in an illustrativeexample to be a single medium, the term “computer-readable storagemedium” should be taken to include a single medium or multiple media(e.g., a centralized or distributed database and/or associated cachesand servers) that store the one or more sets of instructions. The term“computer-readable storage medium” shall also be taken to include anymedium that is capable of storing, encoding or carrying a set ofinstructions for execution by the machine and that cause the machine toperform the methods described herein. The term “computer-readablestorage medium” shall accordingly be taken to include, but not belimited to, solid-state memories, optical media and magnetic media.

FIG. 6 is a block diagram of an example apparatus 610 that may performone or more of the operations described herein, in accordance with someembodiments. The apparatus 610 includes a processing device 611 and amemory 612. The processing device 611 may be operatively coupled to thememory 612. The processing device 611 may analyze computing resourcesused by an application development system 620 during different stages ofa development pipeline for an application. The application developmentsystem comprises a set of computing resources 621. The processing device611 may also determine a current resource usage for a current stage ofthe development pipeline for the application. The processing device mayfurther determine an estimated resource usage for a later stage of thedevelopment pipeline for the application. The processing device mayfurther configure the set of computing resources 621 of the applicationdevelopment system 620 of the later stage of the development pipelinefor the application based on the estimated resource usage

Unless specifically stated otherwise, terms such as “analyzing,”“determining,” “configuring,” “providing,” or the like, refer to actionsand processes performed or implemented by computing devices thatmanipulates and transforms data represented as physical (electronic)quantities within the computing device's registers and memories intoother data similarly represented as physical quantities within thecomputing device memories or registers or other such informationstorage, transmission or display devices. Also, the terms “first,”“second,” “third,” “fourth,” etc., as used herein are meant as labels todistinguish among different elements and may not necessarily have anordinal meaning according to their numerical designation.

Examples described herein also relate to an apparatus for performing theoperations described herein. This apparatus may be specially constructedfor the required purposes, or it may comprise a general purposecomputing device selectively programmed by a computer program stored inthe computing device. Such a computer program may be stored in acomputer-readable non-transitory storage medium.

The methods and illustrative examples described herein are notinherently related to any particular computer or other apparatus.Various general purpose systems may be used in accordance with theteachings described herein, or it may prove convenient to construct morespecialized apparatus to perform the required method steps. The requiredstructure for a variety of these systems will appear as set forth in thedescription above.

The above description is intended to be illustrative, and notrestrictive. Although the present disclosure has been described withreferences to specific illustrative examples, it will be recognized thatthe present disclosure is not limited to the examples described. Thescope of the disclosure should be determined with reference to thefollowing claims, along with the full scope of equivalents to which theclaims are entitled.

As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”,“comprising”, “includes”, and/or “including”, when used herein, specifythe presence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof. Therefore, the terminology usedherein is for the purpose of describing particular embodiments only andis not intended to be limiting.

It should also be noted that in some alternative implementations, thefunctions/acts noted may occur out of the order noted in the figures.For example, two figures shown in succession may in fact be executedsubstantially concurrently or may sometimes be executed in the reverseorder, depending upon the functionality/acts involved.

Although the method operations were described in a specific order, itshould be understood that other operations may be performed in betweendescribed operations, described operations may be adjusted so that theyoccur at slightly different times or the described operations may bedistributed in a system which allows the occurrence of the processingoperations at various intervals associated with the processing.

Various units, circuits, or other components may be described or claimedas “configured to” or “configurable to” perform a task or tasks. In suchcontexts, the phrase “configured to” or “configurable to” is used toconnote structure by indicating that the units/circuits/componentsinclude structure (e.g., circuitry) that performs the task or tasksduring operation. As such, the unit/circuit/component can be said to beconfigured to perform the task, or configurable to perform the task,even when the specified unit/circuit/component is not currentlyoperational (e.g., is not on). The units/circuits/components used withthe “configured to” or “configurable to” language include hardware—forexample, circuits, memory storing program instructions executable toimplement the operation, etc. Reciting that a unit/circuit/component is“configured to” perform one or more tasks, or is “configurable to”perform one or more tasks, is expressly intended not to invoke 35 U.S.C.112, sixth paragraph, for that unit/circuit/component. Additionally,“configured to” or “configurable to” can include generic structure(e.g., generic circuitry) that is manipulated by software and/orfirmware (e.g., an FPGA or a general-purpose processor executingsoftware) to operate in manner that is capable of performing the task(s)at issue. “Configured to” may also include adapting a manufacturingprocess (e.g., a semiconductor fabrication facility) to fabricatedevices (e.g., integrated circuits) that are adapted to implement orperform one or more tasks. “Configurable to” is expressly intended notto apply to blank media, an unprogrammed processor or unprogrammedgeneric computer, or an unprogrammed programmable logic device,programmable gate array, or other unprogrammed device, unlessaccompanied by programmed media that confers the ability to theunprogrammed device to be configured to perform the disclosedfunction(s).

The foregoing description, for the purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the embodiments and its practical applications, to therebyenable others skilled in the art to best utilize the embodiments andvarious modifications as may be suited to the particular usecontemplated. Accordingly, the present embodiments are to be consideredas illustrative and not restrictive, and the invention is not to belimited to the details given herein, but may be modified within thescope and equivalents of the appended claims.

What is claimed is:
 1. A method, comprising: analyzing historicalresource usage of an application development system during differentstages of a development pipeline for an application, wherein theapplication development system comprises a set of computing resourcesand wherein the set of computing resources comprises storage space;determining a current resource usage for a current stage of thedevelopment pipeline for the application; determining an estimatedresource usage comprising an amount of storage space for a later stageof the development pipeline for the application in view of one or moreof the current resource usage or the historical resource usage;reserving a subset of the set of computing resources in view of theestimated resource usage for the later stage of the development pipelineto prevent other processes from utilizing the subset of the set ofcomputing resources, the subset of the set of computing resourcescomprising the amount of storage space; and configuring, by a processingdevice, the subset of the set of computing resources of the applicationdevelopment system for the later stage of the development pipeline inview of the estimated resource usage.
 2. The method of claim 1, whereinanalyzing the historical resource usage of the application developmentsystem comprises analyzing the computing resources used in one or moreof: a unit testing stage; an integration testing stage; a system testingstage; and a deployment stage.
 3. The method of claim 1, whereinanalyzing the historical resource usage of the application developmentsystem comprises: analyzing computing resources used by the applicationdevelopment system for other applications.
 4. The method of claim 1,wherein the current stage comprises a unit testing stage and wherein thelater stage comprises an integration testing stage.
 5. The method ofclaim 1, wherein the current stage comprises an integration testingstage and wherein the later stage comprises a system testing stage. 6.The method of claim 1, wherein the current stage comprises a systemtesting stage and the later stage comprises a deployment stage.
 7. Themethod of claim 1, wherein the computing resources comprise one or moreof: memory; processing power; network bandwidth; and client devices. 8.The method of claim 1, further comprising: determining whether the setof computing resources is sufficient for the later stage of thedevelopment pipeline in view of the estimated resource usage.
 9. Themethod of claim 8, wherein the set of computing resources is configuredin response to determining that the set of computing resources issufficient in view of the estimated resource usage.
 10. The method ofclaim 8, further comprising: providing an indication that the set ofcomputing resources is insufficient in response to determining that theset of computing resources is insufficient in view of the estimatedresource usage.
 11. The method of claim 1, wherein the estimatedresource usage for the later stage of the development pipeline isautomatically determined during the current stage of the developmentpipeline for the application.
 12. An apparatus, comprising: a memory tostore data; a processing device operatively coupled to the memory, theprocessing device to: analyze historical resource usage of anapplication development system during different stages of a developmentpipeline for an application, wherein the application development systemcomprises a set of computing resources and wherein the set of computingresources comprises storage space; determine a current resource usagefor a current stage of the development pipeline for the application inview of one or more of the current resource usage or the historicalresource usage; determine an estimated resource usage comprising anamount of storage space for a later stage of the development pipelinefor the application; reserve a subset of the set of computing resourcesin view of the estimated resource usage for the later stage of thedevelopment pipeline to prevent other processes from utilizing thesubset of the set of computing resources, the subset of the set ofcomputing resources comprising the amount of storage space; andconfigure the subset of the set of computing resources of theapplication development system for the later stage of the developmentpipeline in view of the estimated resource usage.
 13. The apparatus ofclaim 12, wherein to analyze the historical resource usage of theapplication development system the processing device is further toanalyze the computing resources used in one or more of: a unit testingstage; an integration testing stage; a system testing stage; and adeployment stage.
 14. The apparatus of claim 12, wherein to analyze thehistorical resource usage of the application development system theprocessing device is further to: analyze computing resources used by theapplication development system for other applications.
 15. The apparatusof claim 12, wherein the current stage comprises a unit testing stageand wherein the later stage comprises an integration testing stage. 16.The apparatus of claim 12, wherein the current stage comprises anintegration testing stage and wherein the later stage comprises a systemtesting stage.
 17. The apparatus of claim 12, wherein the current stagecomprises a system testing stage and the later stage comprises adeployment stage.
 18. The apparatus of claim 12, wherein the processingdevice is further to: providing an indication that the set of computingresources is insufficient in response to determining that the set ofcomputing resources is insufficient in view of the estimated resourceusage.
 19. A non-transitory computer-readable storage medium includinginstructions that, when executed by a processing device, cause theprocessing device to: analyze historical resource usage of anapplication development system during different stages of a developmentpipeline for an application, wherein the application development systemcomprises a set of computing resources and wherein the set of computingresources comprises storage space; determine a current resource usagefor a current stage of the development pipeline for the application;determine an estimated resource usage comprising an amount of storagespace for a later stage of the development pipeline for the applicationin view of one or more of the current resource usage or the historicalresource usage; reserve a subset of the set of computing resources inview of the estimated resource usage for the later stage of thedevelopment pipeline to prevent other processes from utilizing thesubset of the set of computing resources, the subset of the set ofcomputing resources comprising the amount of storage space; andconfigure, by the processing device, the subset of the set of computingresources of the application development system for the later stage ofthe development pipeline in view of the estimated resource usage. 20.The non-transitory computer-readable storage medium of claim 19, whereinthe processing device is further to: provide an indication that the setof computing resources is insufficient in response to determining thatthe set of computing resources is insufficient in view of the estimatedresource usage.